Skip to content

Conversation

MikeMcC399
Copy link

Situation

.npmrc defines

registry=http://registry.npmjs.org/

The default registry is https://registry.npmjs.org/

Executing npm install provokes a warning message, showing that the setting has been deprecated since the year 2021:

npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/

Change

@MikeMcC399
Copy link
Author

MikeMcC399 commented Aug 22, 2025

@jennifer-shehane / @AtofStryker

If you have cycles available at the moment to review and merge some updates in this repo, I would go ahead and submit non-urgent PRs to put this repo on a more solid footing if it needs changes and releases in the future.

At the moment it would be very hard to cut a release here. Edit: This sentence originally said the opposite of what I meant to write. I wanted to express the fact that there would be a problem to release a new version!

Considering that it is an essential npm package for some Cypress Cloud features it would be beneficial to do some maintenance on it.

@MikeMcC399
Copy link
Author

@AtofStryker

Thank you for approving! Will you or somebody else now merge this PR, so I can rebase the other work on this one?

In the previous comment I originally accidently wrote the opposite of what I meant. The current state of this repo means that it is not possible to release any changes. The minimum goal I would like to reach is that updates to the repo could be released if necessary. There are several steps necessary to clean this up and get to a solid base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants